Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Preface

This Preface contains the following sections:

Purpose
Audience
Organization
Typographical conventions
OpenEdge messages

Purpose

This manual describes how to configure and manage Progress Dynamics®. It also describes a common set of administrative procedures that you might need to perform to support all of the applications that you develop using Progress Dynamics.

Audience

This manual is designed for Progress Dynamics programmers who have some familiarity with the Progress® ADM.

Organization

Chapter 1 "Overview of Progress Dynamics Administration"

Describes the basic administrative tasks and tools.

Chapter 2 "Defining and Managing Sessions"

Describes how to create and configure Progress Dynamics sessions, which are runtime and development environments for applications.

Chapter 3 "Setting Up Basic Security Options"

Shows the requirements and how to install Progress Dynamics on your system and configure it for basic operation.

Chapter 4 "Supporting Built-in Application Features"

Describes how to prepare several application features that are partly or completely built into Progress Dynamics that you can set up to work in your own applications.

Chapter 5 "Extending the Progress Dynamics Configuration Utility"

Describes how to extend the Dynamics Configuration Utility (DCU) in order to deploy your own Dynamics applications, including information on running the DCU in batch mode and saving site-specific data during an application installation or upgrade.

Appendix A, "Using OpenEdge DataServers with Progress Dynamics"

Describes some of the factors you should consider when using a OpenEdge® DataServer™ in the Progress Dynamics environment.

Appendix B, "Progress Dynamics Session Properties"

Describes describes the Progress Dynamics session properties.

Appendix C, "Inside the Progress Dynamics Configuration File"

Describes the contents of the default configuration file to help you gain an understanding of what this XML file does.

Appendix D, "Deployment Notes"

Describes deployment features that supplement the features described in the deployment white paper posted on the Progress Software Developers Network® (PSDN) Web site (http://psdn.progress.com).

Appendix E, "Performance Notes"

Describes features that enable you to improve Progress Dynamics application performance, depending on your application design and deployment requirements.

Typographical conventions

This manual uses the following typographical conventions:

Convention	Description
Bold	Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements.
Italic	Italic typeface indicates the title of a document, or signifies new terms.
SMALL, BOLD CAPITAL LETTERS	Small, bold capital letters indicate OpenEdge® key functions and generic keyboard keys; for example, GET and CTRL.
KEY1+KEY2	A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X.
KEY1 KEY2	A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H.
Syntax:
Fixed width	A fixed-width font is used in syntax statements, code examples, system output, and filenames.
Fixed-width italics	Fixed-width italics indicate variables in syntax statements.
Fixed-width bold	Fixed-width bold indicates variables with special emphasis.
UPPERCASE fixed width	Uppercase words are Progress® 4GL language keywords. Although these are always shown in uppercase, you can type them in either uppercase or lowercase in a procedure.
	This icon (three arrows) introduces a multi-step procedure.
	This icon (one arrow) introduces a single-step procedure.

OpenEdge messages

OpenEdge displays several types of messages to inform you of routine and unusual occurrences:

Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value.
Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database.
Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.

After displaying a message, OpenEdge proceeds in one of several ways:

Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages.
Returns to the Progress Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages.
Halts processing of a procedure and returns immediately to the Progress Procedure Editor. This does not happen often.
Terminates the current session.

OpenEdge messages end with a message number in parentheses. In this example, the message number is 200:

** Unknown table name table. (200)

If you encounter an error that terminates OpenEdge, note the message number before restarting.

Obtaining more information about OpenEdge messages

In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages:

Choose Help Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session.
Choose Help Messages and then type the message number to display a description of a specific OpenEdge message.
In the Progress Procedure Editor, press the HELP key or F1.

On UNIX platforms, use the Progress pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.

To use the pro command to obtain a message description by message number:

Start the Progress Procedure Editor:

install-dir/dlc/bin/pro

Press F3 to access the menu bar, then choose Help Messages.
Type the message number and press ENTER. Details about that message number appear.
Press F4 to close the message, press F3 to access the Progress Procedure Editor menu, and choose File Exit.